|
Release 0.2 of the Execution Framework |
|
|
|
Written by Administrator
|
|
Wednesday, 07 July 2004 |
|
The OSEK release of the COMPARE Execution Framework is available for COMPARE developers. |
|
Last Updated ( Monday, 17 July 2006 )
|
|
|
Release 0.1 of the Execution Framework |
|
|
|
Written by Administrator
|
|
Wednesday, 07 July 2004 |
|
A first release of the COMPARE Execution Framework is available for COMPARE developers. |
|
Last Updated ( Monday, 18 July 2005 )
|
|
|
Welcome to COMPARE Embedded Components |
|
|
|
Written by Web Master
|
|
Saturday, 12 June 2004 |
|
If you've read anything at all about software components you will know at least two things: i) components are expected to solve the software reusability problem and ii) components are big, slugguish and opaque pieces of code.
|
The IST COMPARE project is set to change this last perception. This website has been created to disseminate COMPARE results but also to catalyse the creation of a community on embedded component technology.
|
| The COMPARE project is being funded by the European Comission through project IST 004669, A COMPonent Approach to Real-time and Embedded.
Get the COMPARE Flyer.
|
|
|
|
Last Updated ( Sunday, 30 October 2005 )
|
|
|
What is a Component? |
|
|
|
Written by Administrator
|
|
Wednesday, 12 May 2004 |
|
Giving a relevant definition of the component concept is an issue which has often been dealt with in the CBSE (Component Based Software Engineering) research field. Heineman defines software component as a software element that conforms to a component model and can be independently deployed and composed without modification according to a composition standard. This definition of components introduces concerns relating to composition and deployment. It will therefore not fit to some approaches within the RT (real-time) domain, in which much more basic constructs are sometime considered as components. Lee gives several examples: subroutine libraries, processes and threads, programming language primitives and their aggregates, etc. Components are considered here as distinct, reusable modules, from which the software is built. Although Heineman's definition is preferred, we do not want to exclude approaches that do not properly support deployment.
|
|
Last Updated ( Monday, 18 July 2005 )
|
|
Read more...
|
|
|
Component Models |
|
|
|
Written by Web master
|
|
Wednesday, 12 May 2004 |
|
The COMPARE State of the Art report gives an overview of existing component models.
Besides their core features, the report investigates their support for the real-time and embedded domain.
Many aspects must be taken into account:
- Basic properties of the model, for instance how required and provided interfaces are specified or whether it supports hierarchical composition.
- Component interaction: i.e. the interaction mechanisms between components, e.g. events or method invocation.
- Possibilities to describe non-functional requirements in particular relating to real-time.
- Underlying execution framework, e.g. its footprint and its availability on certain real-time operating systems and processor combinations.
- Packaging, deployment and configuration.
- Development environment
- Summary with the pros and cons of the approach.
|
|
Last Updated ( Monday, 18 July 2005 )
|
|
Read more...
|
|
|
|
<< Start < Prev 1 2 3 Next > End >>
|
| Results 19 - 23 of 23 |
